Disk control unit and storage system

ABSTRACT

Provided is a disk controller comprising a front end FC I/F to a host, a back end FC I/F to a magnetic disk, a processor, and a main memory section. The front end I/F and the back end I/F are provided for performing information exchange with a network (connected) device that is connected to a network and manages storage. The main memory section stores registered information expressing an attribution of the network (connected) device, access information including security and performance of each network (connected) device through the network, and ranking information assigning a rank to each network (connected) device based on the registered information and the access information. An appropriate network (connected) device is selected from various types of information including the ranking information.

CROSS-REFERENCES TO RELATED APPLICATIONS

The present application is a continuation of application Ser. No.10/923,732, filed Aug. 24, 2004; which is a continuation of applicationSer. No. 10/852,111, filed May 25, 2004, now U.S. Pat. No. 7,302,498;which relates to and claims priority from Japanese Patent ApplicationNo. 2004-082824, filed on Mar. 22, 2004, the entire disclosure of whichis incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a storage system, and a managementmethod for such storage system, having a disk controller and an iSCSIdevice connected to the disk controller by a network. More particularly,the present invention relates to a format for managing storageconnections on the network.

2. Description of the Related Art

As IT becomes more widespread and entrenched, users continue to seekgreater storage capacity. Because of this, there are many cases wheremore storage is necessary than the capacity originally installed in astorage system.

FIG. 8 shows an example of an overall construction of a disk controllerand a storage system in accordance with a conventional example. In theconventional technique shown in FIG. 8, an operation input and amanagement program 235 on an SVP (Service Processor) 230 issue aninstruction to a control program 217 and a device list 218 inside a diskcontroller 210 to register new storage as storage to be governed by thedisk controller 210 itself, and to connect a corresponding new magneticdisk 220 to a back end FC I/F 213, whereby achieving extension ofstorage capacity.

In another method for increasing storage capacity, instead of themagnetic disk 220, FC heterogeneous storage 227 having an FC device 225is connected. Here, “storage” refers collectively to magnetic disks,magnetic tape, etc. “Heterogeneous storage” refers to any storage mediumthat the disk controller does not manage directly. Also, “FC” is anabbreviation for Fiber Channel. An example of an FC storage system isillustrated in an IBM white paper called “IBM Storage Tank™, ADistributed Storage System”, dated Jan. 24, 2002.

As shown in FIG. 8, when making a remote copy or a backup of data, thestorage where the remote copy is to be made does not necessarily have tobe recognized by the disk controller as storage governed by the diskcontroller 210 itself. Therefore, it is also possible to use a SAN(Storage Area Network) 250 to connect a heterogeneous storage 229 havinga front end FC I/F 212 and an FC device 260. An example of such aconstruction is disclosed in U.S. Pat. No. 6,092,066.

On the other hand, in an IP network, transmissions can only be performedin accordance with TCP/IP protocol, for example. Therefore, in order todirectly send SCSI protocol, which is common for disk unit I/O, the diskunit, a new protocol is necessary to piggyback common SCSI commands andthe like onto the data portion of an IP frame. A representative exampleof this new protocol is iSCSI protocol.

An example of a storage system using iSCSI is shown in U.S. Pat. No.5,996,024. This type of iSCSI I/F can transmit information about amagnetic disk, which is the target, to the disk controller, which is aninitiator. In the storage system using the FC I/F as described above,the network is closed inside the disk controller. Therefore, since it ispossible to learn the status of everything including the status of theFC heterogeneous storage and the status along the route thereto, it ispossible to select the optimum storage when recording data.

However, in the FC I/F storage system described above, it is notpossible to connect an IP network and iSCSI heterogeneous storage thatare spread widely around the world. Therefore, in order to create anetwork on an IP-network scale, it is necessary to set up a separatenetwork with just the FCs. Furthermore, management methods used on IPnetworks cannot be simply transferred and used on the storage systemusing the FC I/F described above.

In order to add more storage using the FCs and the SAN as disclosed inU.S. Pat. No. 6,092,066, it is necessary to establish the SAN networkseparately from the general IP network. This creates problems ofincreased equipment costs and management costs.

On the other hand, with the iSCSI I/F using the IP network, the iSCSIstorage can be connected as the target, but only information about thetarget can be transmitted. Therefore, it is not possible to learninformation about the performance of the network leading to the iSCSIstorage, nor security, costs, or other such information about the IPnetwork. Therefore, there was a problem in that it was not possible toconnect optimally to the iSCSI heterogeneous storage in a way which tookthe status of the network into consideration.

SUMMARY OF THE INVENTION

In order to solve the above-mentioned problems, the present inventionadopts mainly the following construction.

In a disk control unit comprising a front end FC I/F which is aninterface to a host, a back end FC I/F which is an interface to amagnetic disk, a processor for controlling each section, and a mainmemory section, a front end I/F and a back end I/F are provided toperform exchanges of information with network (connected) devices thatare connected to a network and manage storage; the main memory sectionstores registered information expressing an attribution of the network(connected) devices, access information including information aboutsecurity and performance of each network (connected) device through thenetwork, and ranking information assigning a rank to each network(connected) device based on the registered information and the accessinformation; and an appropriate network (connected) device is selectedfrom various types of information including the ranking informationstored in the main memory section, based on a condition requested by thecomputer.

In the disk control unit, communication with the network (connected)devices uses iSCSI protocol or IP protocol.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram showing an example of an overall construction ofEmbodiment 1 of a disk controller and a storage system;

FIG. 2 is a structural diagram of a device list in accordance withEmbodiment 1 of the device control unit;

FIG. 3 is a flow chart showing an example of device registration,testing, updating and accessing between the disk controller and an iSCSIdevice in accordance with Embodiment 1;

FIG. 4 is a diagram showing a flowchart of device registration, testing,updating and accessing by a storage broker device inside the diskcontroller in accordance with Embodiment 1;

FIG. 5 is a diagram showing a flowchart of iSCSI device registration,test reporting and a device list change, in accordance with Embodiment1;

FIG. 6 is a diagram showing an example of mirroring, backing up andstorage of system log data in accordance with Embodiment 1 of the diskcontroller;

FIG. 7 is a flowchart showing an example of device registration,testing, updating and accessing between a disk controller and an iSCSIdevice in accordance with Embodiment 2 of the disk controller; and

FIG. 8 is a diagram showing an overall construction of a disk controllerand storage system in accordance with a conventional example.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Embodiments of a disk controller of the present invention are explainedin detail below, with Embodiment 1 and Embodiment 2 given as examples,and with reference made to the diagrams.

FIG. 1 is a diagram showing an overall construction of Embodiment 1 of adisk controller and a storage system. In FIG. 1, a host 1 (100) and ahost 2 (101) are connected to a disk controller 110 via a front end FCI/F 111, and can read and write data using FC protocol. The diskcontroller 110 controls data between the computer (below, “host”) 100and the host 2 (101) and a magnetic disk 120. Furthermore, inside thedisk controller 110, there is provided a front end iSCSI I/F 112, whichis an interface to IP networks 150, 151, 152. Here, the front end iSCSII/F 112 is used, for example, as an interface to heterogeneous storage(any storage which is not directly managed by the disk controller) formaking a remote copy or a backup of data.

The disk controller 110 has a back end FC I/F 113 as an interface to themagnetic disk 120, and the magnetic disk 120 is connected to the backend FC I/F 113. Furthermore, the disk controller 110 has a back endiSCSI I/F 114 and is connected to a magnetic disk 121, and the magneticdisk 121 is managed directly. Furthermore, the disk controller 110 hasthe back end iSCSI I/F 114 as an interface to iSCSI devices 160, 170 onthe network, which are external devices connected via the networks 150,151, 152. In other words, a router 140 or the iSCSI devices 160, 170 areconnected to the backend iSCSI I/F 114 as devices on the network. Here,the router 140 may also be a network switch.

Furthermore, the iSCSI devices 160, 170 are connected to the front endiSCSI I/F 112 inside the disk controller 110 via the router 14 and thenetworks 150, 151, 152. Information is exchanged between the front endand the iSCSI devices. Furthermore, a cache memory 119 is provided alongthe route where the data is transferred from the front end FC I/F 111 tothe back end FC I/F 113. The cache memory is used for high-speed dataaccess.

The entire disk controller 110 is controlled by a control processor 115.Programs, tables, lists, etc. are stored in a main memory 116.Furthermore, in order to enable structural changes, monitoring,controls, etc. to be made to the disk controller 110 from an externallocation, the disk controller 110 is provided with a SVP (serviceprocessor) 130 containing a management program 135. The SVP is connectedto the control processor 115. The SVP 130 may be subordinate to the diskcontroller 110 and perform functions of a personal computer. In thiscase, a user can give instructions to the control processor 115 byperforming input operations on the SVP 130. Furthermore, the SVP 130 maybe connected to the disk controller 110 via a network and performfunctions similar to the hosts. Among the programs stored in the mainmemory 116, there is a storage broker 117 as a program according to thepresent invention. This program performs control of the iSCSI devices.Moreover, the main memory 116 has a device list 115 serving as adatabase storing information that is necessary when connecting to theiSCSI devices 160, 170.

The front end iSCSI I/F 112 and the back end iSCSI I/F 114 are connectedvia the router 140 to the networks 150, 151, 152, and the router 140sends IP packets from each interface to the networks 150, 151, 152 insuch a manner as correctly corresponds to the addresses of the IPpackets. On the other hand, the iSCSI devices 160, 170 are connected tothe networks 150, 151, 152. Inside the iSCSI devices 160, 170 areprovided storage broker replying (micro) programs 165, 175 as programsfor exchanging information with the storage broker 117.

The storage connected to the iSCSI devices 160, 170 includes, forexample, iSCSI heterogeneous storage 167 and a heterogeneous magnetictape disk 125 and the like, which are not directly managed by the diskcontroller 110. Thus, by connecting the disk controller 110 and theiSCSI heterogeneous storage 167 and the like, it becomes possible tofreely add voluminous storage beyond the capacity of the FC I/F magneticdisk 120 that is under the direct management of the disk controller 110.

Furthermore, for information about the networks 150, 151, 152 (e.g.,their performance, security, cost, etc.) it is possible to useinformation stored in the router 140. This information can be utilizedby applying the protocol that is normally used. SNMP is for example.Information about the iSCSI devices 160, 170 can be collected duringnegotiation and other procedures performed during iSCSI Loginprocessing. Ranking of the iSCSI devices 160, 170 will be explainedbelow, using a device list in FIG. 2.

Here, the device registration, deletion, test accessing andtransmission/reception of data that the storage broker 117 of the diskcontroller 110 performs over the network with the storage brokerreplying (micro) programs 165, 175 in the iSCSI devices 160, 170 areperformed via the front end iSCSI I/F 112 or the back end iSCSI I/F 114.That is, based on an instruction from the control processor 115 thatcontrols the overall disk controller 110, the storage broker 117 sends adevice registration request and the like (see step 400 in FIG. 3described below) through the front end iSCSI I/F 112 or the back endiSCSI I/F 114 to the iSCSI devices 160, 170.

Methods for the control processor 115 to manage the iSCSI devices 160,170 on the network include: a first method, in which the controlprocessor 115 manages everything just like the magnetic disk 121 whichthe control processor 115 itself governs, or a second method, in whichthe management is yielded to the iSCSI device. If the first method isused, the control processor itself manages the iSCSI devices 160, 170 onthe network, so data distribution and other detailed controls becomepossible. If the second method is used, the control processor yields thedata management to the iSCSI devices on the network, and thus it becomespossible to reduce the control processor's management overhead. Whetherto use the first method or the second method may be determined by thecontrol processor based on it's own load, or by an instruction from theSVP by the user.

Here, the device registration, deletion, test accessing andtransmission/reception of data that the storage broker 117 performs withthe storage broker replying (micro) programs 165, 175 of the iSCSIdevices 160, 170 on the network are executed according to controls bythe control processor 115. However, the control processor can use eitherthe front end iSCSI I/F 112 or the back end iSCSI I/F 114 to execute theregistration, etc. Basically, it is not necessary to distinguish betweenusage the front end I/F and the back end I/F, so either end I/F may beused. In a typical example of usage, for backing up and for remotecopying, the control processor may perform controls so that the frontend I/F is used. For adding disks (this is process enables the diskcontroller to use heterogeneous storage present broadly through the IPnetwork) controls may be performed to use the back end I/F (adding amagnetic disk to be managed directly by the control processor is similarto the normal processing method using the back end I/F.) Furthermore,whether to use the front end I/F or the back end I/F may be determinedby the control processor according to an instruction from the SVP madeby the user.

As shown in FIG. 1, each of the iSCSI devices 160, 170 can be connectedto each of the networks 150, 151, 152 as a way to deal with a case wherean accident occurs on one of the networks. In FIG. 1, the X mark on theconnection line between the network and the iSCSI device indicates anetwork accident. Also, in FIG. 1, in response to the data write requestfrom the host, the disk controller 110 generally selects the magneticdisks 120, 121 that are directly managed by the disk controller, but inthe case of a request to write voluminous data that cannot all be storedon the magnetic disks 120, 121, or in a case where the capacity of emptyspace on the magnetic disks 120, 121 has become small, or in a casewhere copy data is to be stored onto a storage medium other than themagnetic disks 120, 121, the data is written onto the externalheterogeneous storage or heterogeneous storage medium via the network.

FIG. 2 is a structural diagram of a device list according to Embodiment1 of the disk controller. In FIG. 2, Rank 310 indicates a priority levelwith which a new connection will be made to each registered iSCSI deviceon the network in response to a request from the host or the SVP.ISCSI-Name 320 indicates an address of each iSCSI device. Capacity ofEmpty Area 330 indicates usable data capacity in each iSCSI device.Transfer Speed or Delay 340 indicates a data transfer speed or amount oftime required to transfer data, which should be expected when accessingeach of the iSCSI devices.

Furthermore, in the device list 118, Security 350 indicates the safetyof the routes from the iSCSI devices 160, 170 to the disk controller110, as determined based on the number of incidences that have occurredthere in the past, the security configured there, etc. Running orResting 360 indicates the current running state of each iSCSI device160, 170. Cost 370 indicates the cost necessary to use each iSCSI device160, 170.

Using each of these entries, the storage broker 117 determines the rankof each of the registered iSCSI devices 160, 170 as relevant to acondition requested by the disk controller 110. Here, the requestedcondition may be, for example, a condition requiring that voluminouswriting be necessary, a condition requiring that the data to be handledbe important or confidential, or a condition requiring that the diskcontroller itself have detected and learned its own load status, forexample, such as how fast or slow its transfer speed is, or the volumethat is too large to write, etc.

An example of a way to determine the rank is to assign ranks to theentries from 320 to 370 for each device, and then, based on thecondition requested by the disk controller 110, assign weight to thoseentries which are considered important, and then total these up tocalculate the ultimate rank. A specific method for assigning the rankscould be, for example to numerically express (standardize) those whichcan be numerically expressed as “Xij” (where “i” represents the devicenames written vertically in FIG. 2, and “j” represents the entrieswritten horizontally in FIG. 2), and then multiply these by weights W1,W2, W3, . . . Wi provided by the SVP 130 (where a greater value of “Wi”indicates greater importance), and then assign the ranks according tothe size of the value (Rank-i) thus produced.

Rank1=W1×X11+W2×X12+W3×X13+ . . .

Rank2=W1×X21+W2×X22+W3×X23+ . . .

There is also a method for expressing those which cannot be numericallyexpressed as rules (such as whether the device is running or resting).For example, the rule may be expressed as “if i=running, then Rank-i=R1;else Rank-i=0 (where R1 is a value determined in advance)”.

Furthermore, since the SVP 130 is connected via the router 140 and thenetworks 150, 151, 152 to each of the iSCSI devices and thus hasconnections similar to the control processor 115, the SVP 130 can alsoperform the ranking of each of the registered iSCSI devices similarly tohow ranking is performed by the control processor 115 as describedabove. The results of the ranking are stored in the device list 118 viathe control processor. Note that it is self-evident that the user canadd entries that are necessary besides those shown in FIG. 2.

FIG. 3 is a flow chart showing an example of device registration,testing, updating and accessing between the disk controller and theiSCSI device on the network in accordance with Embodiment 1. In FIG. 3,first, a device registration start command is transmitted from one ofthe hosts 100, 101 or the SVP 130 to the disk controller 110 (405). Thecontrol processor 115 of the disk controller 110 issues an iSCSI deviceregistration request to the network's iSCSI devices 160, 170 and storagebroker replying (micro) programs 165, 175 (400). The iSCSI devices 160,170 that received the request then register their own device information(410). Next, based on controls by the control processor 115, the storagebroker 117 registers the iSCSI device(s) that replied into the devicelist 118 (420).

Then, the storage broker 117 assigns ranks to the information of theregistered iSCSI devices (430). Furthermore, the storage broker 117performs a test access to the registered iSCSI devices(s) or the router140 that is en route thereto, and collects information about the networkstatus, etc. (440).

The router 140 or iSCSI devices 160, 170 on which the test access wasperformed then reply to the test access (450). If the iSCSI devices 160,170 have had their own device information (e.g., their capacity of emptyarea, etc.) updated, they register the change in information with thestorage broker 117 (455). Once the information is finished being changedwith the storage broker 117, the storage broker 117 assigns ranks to theiSCSI device information once again (460).

After that, when a device request to add a device or create a journallog or perform a backup or a remote copy is sent to the storage broker117 from an external location (e.g., the host or SVP) (470), aconnection is then established to the iSCSI device with the highest rankand this device is registered (475). When this registration isperformed, the registered iSCSI device also changes the registration ofits own device information (476).

Here, step 475 is processing to add new storage to the disk device thatis already present and under the management of the disk controller. Thedecision to add the storage is made according to the capacity of themagnetic disks being managed by the disk controller. That is, therequest to add the storage is made when the existing disk capacity willnot satisfy the write request from the host (when safety factors arealso considered). Also, in addition to the current disk capacity, thedecision to add the storage can also be made according to the I/Otransaction number, transfer rate, control processor usage rate or otheraspect of the performance of the disk controller itself. That is, amethod is used in which the disk controller judges the decrease in theI/O transaction number or the like and then yields the storagemanagement to the iSCSI devices, and the new storage is added.

Then, the storage broker 117 chooses the iSCSI device with the highestrank in the device list 118, and according to this selection the diskcontroller 110 performs the iSCSI login and the data access (480). Theaccessed iSCSI device 160, 170 then performs normal iSCSI commandprocessing (490). After that, the processing performed by the storagebroker 117 returns to 440, and the storage broker replying (micro)programs 165, 175 return to 450.

Note that the disk controller can also perform deletion of theregistered iSCSI device as part of the normal processing. When theregistered iSCSI device breaks down, or the network performance of theiSCSI device deteriorates, the disk controller performs processing todelete the information for the corresponding iSCSI device from thedevice list and inform the iSCSI device that it has been cut off fromthe disk controller.

Thus, by performing the test registration and the testing via the routerand the network, the disk controller can obtain the information aboutthe devices connected on the network and the security information thatis obtained when each device is accessed, etc. Based on thisinformation, the devices are then ranked, which is then stored in thedevice list serving as the database. The optimum network device can thenbe selected based on the rankings in the device list. Note that, incertain cases (such as when there is a request from the user) thenetwork device can be selected according to items other than therankings.

FIG. 4 is a diagram showing a flowchart of registration, testing,updating and accessing by the storage broker device in accordance withEmbodiment 1. In FIG. 4, first, in response to the device registrationrequest from the host 100, 101 or the SVP 130, the registration of theiSCSI device in the disk controller 110 (or, more specifically, in thestorage broker 117) is started (500). Next, the disk controller 110broadcasts the iSCSI device registration request on the network (510).The disk controller 110 registers the iSCSI device that replied into thedevice list 118 (515), and assigns the rank within the registered devicelist 118 (520). The test access is then performed on the registereddevice or the router 140 (535). Next, a check is performed to determinewhether or not the device list 118 needs to be updated (540).

If the update is necessary, then the disk controller 110 re-assigns theranks to the devices in accordance with the update information (545). Ifan update is not necessary, then the check is performed to determinewhether or not there is device list update information from an externallocation (550). If an update is necessary, then the ranks arere-assigned to the devices in accordance with the update information(555). If the update is not necessary, then a check is performed todetermine whether or not there are various types of device requests(560). If a device request has occurred, then a connection is made tothe iSCSI device with the highest rank and this device is registered(561). The processing at step 561 corresponds to the processing at step475 shown in FIG. 3, and the judgment to add the newly connected storageis made similarly to that in step 475 in FIG. 3. Next, based on theoccurrence of the device request, the iSCSI Login and the data accessare then executed for the optimum device in the device list 118 (565).If there is no request, or after the request processing is completed,then the procedure returns to test access A at 535 (570).

FIG. 5 is a diagram showing a flowchart of iSCSI device registration,test reporting and a device list change, in accordance withEmbodiment 1. In FIG. 5, first, the iSCSI device starts iSCSI deviceprocessing (600). Next, the iSCSI device collects its own iSCSI deviceinformation and registration conditions (610). Next, the iSCSI devicechecks to determine whether or not there is a device list registrationrequest from the disk controller (615). If there is a registrationrequest, then the device information is registered into thecorresponding storage broker 117 in the disk controller. Next, the iSCSIdevice checks to determine whether or not a test access has beenperformed from an outside location (625). If access has been performed,then the iSCSI device replies to the storage broker 117 with the resultsof the access test (630). Furthermore, the iSCSI device checks todetermine whether or not the update list 118 needs to be updated (635).If the update is necessary, then the registered information is updatedin the corresponding storage broker 117 (640).

Next, the iSCSI device checks whether the device has been accessed(645). If the device has been accessed, then normal iSCSI device targetprocessing is performed (650). If the device has not been accessed, thenthe procedure returns to step 610 where the iSCSI device collects itsown iSCSI device information and registration conditions.

FIG. 6 is a diagram showing an example of mirroring, backing up andsystem log data storage in accordance with Embodiment 1 of the diskcontroller. In FIG. 6, when mirroring is to be performed, data A 800 isstored as master data on the magnetic disk 120. On the other hand, dataA 850 is stored as slave data in the iSCSI heterogeneous storage 167 asthe data A 850. When this is performed, the data A 800 and the data A850 are synchronized.

When a backup is to be performed, data C 820 is stored as master data onthe magnetic disk 120. On the other hand, backup data is stored as olddata C 870 in the iSCSI heterogeneous storage 167. Furthermore, the diskcontroller records the storage system's access status. When an accidentoccurs, the old data C 870 from the backup data is used, and system logdata 880 for restoring the original data is stored onto a magnetic disk125 where broad capacity is available in the first place.

As explained above, when Embodiment 1 of the disk controller is used,wide-ranging storage connected to the IP network becomes usable, and thedesired storage capacity can be realized. Note that, Embodiment 1 wasexplained with respect to the construction in which the disk controllerhas the magnetic disk 120 which the disk controller manages directly.However, in the disk controller of Embodiment 1, the subject of theinvention is that it can be connected over the network to the storage orthe magnetic disks. Therefore, the present invention is not restrictedto the construction explained above. A construction which does not havethe directly managed magnetic disk naturally falls within the scope ofthe present invention as well. (This is also the same for Embodiment 2.)

FIG. 7 is a diagram showing an example of device registration, testing,updating and accessing between a disk controller and an iSCSI device inaccordance with Embodiment 2. In FIG. 7, first, a command to startdevice registration is sent to the disk controller 110 from one of thehosts 100, 101 or the SVP 130 (805). Next, device list registration isperformed according to an operation input from the SVP 130 or themanagement program 135 (800). Then, the disk controller 110 performs atest access to the iSCSI device or the router, obtains necessaryinformation, and transmits this to the SVP 130. Next, if there is achange in the iSCSI device information (such as a change in the capacityof empty area) (855), the storage broker 117 assigns the device ranks inaccordance with this update information (860), and then transmits theserankings to the SVP.

In FIG. 7, all of the data to be written into the device list 118 isdisclosed from the SVP 130 (800, 840, 860). In other words, inEmbodiment 2, the SVP 130 gives instructions for the processing of step400 (the iSCSI device registration request), step 410 (the device's owninformation registration), and step 420 (the registration of the iSCSIdevice that replied into the device list), which are shown in FIG. 3.The subsequent data flow is similar to FIG. 3.

Thus, when Embodiment 2 is used, the procedures can progress withoutspending time on registering and checking the devices. Furthermore, theranking of the registered iSCSI devices can also be performed by the SVP130 like the ranking performed by the control processor 115 as describedabove. (See the description of ranking in Embodiment 1.)

As explained above, the disk controller of the present invention can besummarized as follows: In a conventional FC device heterogeneousconnection, iSCSI devices connected on a common IP network cannot beused to connect heterogeneous storage. Furthermore, when FCs are used tobuild a SAN, equipment costs become expensive, and in a case wherecommon iSCSI devices are connected, it is difficult for the diskcontroller side to accurately learn the status of the devices, so theheterogeneous connection could not be established easily. In order toovercome these problems, in the present invention, the device list isprovided inside the disk controller in order to register the status ofthe externally connected IP network, the capacity of the iSCSI devices,the transfer rate, security, etc., and to assign the ranks. Furthermore,at regular intervals the storage broker in the disk controller updatesthe various conditions. When the request is made for the needed iSCSIdevice, the iSCSI device is connected based on the device list. Thus, itbecomes possible to always select the optimum iSCSI device in terms ofcapacity, performance, security and cost. It also becomes possible toperform the optimum heterogeneous storage connection on the IP network.

In accordance with the present invention, the iSCSI I/F can be used tooptimally select from many heterogeneous storage entities existingexternally via the IP network. Therefore, costs can be reduced andstorage capacity can be expanded.

1. A disk control unit comprising: a plurality of interfaces (I/Fs); aprocessor for controlling the plurality of I/Fs; and a main memorysection, wherein the plurality of I/F exchange information with aplurality of Internet Small Computer System Interface (iSCSI) devicesvia a network connected between the iSCSI devices and the plurality ofI/Fs, wherein each of the iSCSI devices manages a storage, wherein themain memory section stores registered information expressing anattribution of each of the iSCSI devices including capacity informationindicating a capacity of the storage of each iSCSI device, accessinformation indicating security and performance of each of the iSCSIdevices through the network, and ranking information assigning a rank toeach of the iSCSI devices based on the registered information and theaccess information, wherein the processor selects an appropriate iSCSIdevice according to various types of information including the rankinginformation stored in the main memory section, wherein said capacityinformation of the storage of each iSCSI device is collected during SCSIlogin processing to said iSCSI devices, and wherein said accessinformation indicating security and performance of each of the iSCSIdevices is collected at a timing of performing a test access to saidiSCSI devices.
 2. The disk control unit according to claim 1, whereincommunication with each of the iSCSI devices uses iSCSI protocol or IPprotocol.
 3. The disk control unit according to claim 1, wherein themain memory section is provided with a storage broker as a controlprogram for performing control on each of the iSCSI device each of whichmanages a storage, and is provided with a device list storing theregistered information, the access information, and the rankinginformation.
 4. The disk control unit according to claim 1, wherein theprocessor obtains the registered information from a replying programbuilt into each of the iSCSI devices, and obtains the access informationupon accessing each of the iSCSI devices via the network.
 5. The diskcontrol unit according to claim 4, wherein a Service Processor (SVP)with a built-in management program is connected to the processor,wherein the processor obtains the registered information and the accessinformation from terminal operations on the SVP, or from the managementprogram.
 6. The disk control unit according to claim 5, wherein theinformation exchange with each of the iSCSI devices is performed via oneof the plurality of I/Fs.
 7. The disk control unit according to claim 5,wherein the information exchange with each of the iSCSI devices isperformed via another one of the plurality of I/Fs.
 8. The disk controlunit according to claim 1, wherein each storage managed by an iSCSIdevice has an iSCSI I/F.
 9. The disk control unit according to claim 4,wherein the processor obtains the registered information and the accessinformation from the network.
 10. The disk control unit according toclaim 1, wherein the processor selects an iSCSI device to which to writemirrored data or backup data based on the registered information, theaccess information and the ranking information.
 11. The disk controlunit according to claim 1, wherein the processor selects an iSCSI deviceto which to write log data accessed from the host based on theregistered information, the access information and the rankinginformation.
 12. A disk control unit according to claim 1, wherein saidprocessor determines, upon receipt of a write request, whether acapacity of a storage of an iSCSI device being used satisfies the writerequest, and wherein said processor requests the iSCSI device being usedto add storage if the capacity of the storage of the iSCSI device beingused does not satisfy the write request.